Support dynamic workflow phases - #19
Merged
Merged
Conversation
Contributor
Author
E2E verification supplementI also ran a local interactive Pi smoke test against this branch. The fixture and session files were temporary local files on my machine only; they are not part of this PR and are not needed to review the change. Setup:
Workflow shape used for the smoke test:
The interactive UI rendered the dynamic phase list without an empty skipped phase row: The saved workflow details had the expected single phase list: {
"phases": ["Initial scan", "Inspect API", "Inspect UI"],
"agentCount": 3,
"doneCount": 3,
"errorCount": 0
}Additional checks:
|
Michaelliv
force-pushed
the
dynamic-workflow-phases
branch
from
May 31, 2026 06:24
ad63f34 to
0a30057
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This aligns the progress UI and tool guidance with what the workflow runtime already supports: phases can be created as the script runs.
meta.phases; progress now follows phases that actually appear during execution.snapshot.phasesas the single runtime phase list; no extra parallel phase state is needed.meta.phasesis clearly optional and conditional/loop-created phases are encouraged when useful.Tests
npm testopenai/gpt-5.5and--thinking low, loading this extension explicitly. The workflow returnedok: true, includedInitial scan,Inspect API, andInspect UI, and left the skippedReviewphase out of the result phases.